-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #5073, #5062, #5099, and part of #1723: Improve Onboarding Documentation #5174
Conversation
- Make steps more linear - Include information that address common setup issues - Add information about running tests
@MohitGupta121, could you PTAL and let me know your thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adhiamboperes LGTM, Thanks!
Very clear and to the point instructions now.
Assigning @BenHenning for code owner reviews. Thanks! |
@seanlip, PTAL for codeowners, (If possible). |
Unassigning @adhiamboperes since a re-review was requested. @adhiamboperes, please make sure you have addressed all review comments. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @adhiamboperes! LGTM. You might need to fix the sidebar merge conflict though.
Explanation
Fix #5073: Add instructions to the wiki for how to assign a reviewer.
Fix #5062: Add wiki documentation for how to pick the emulator/android version when running Espresso tests.
Fix #5099: Reorganize the Project Setup Documentation
Fix part of #1723: ensure the onboarding flow leads into follow-up documentation: architecture overview, code style, submission guidelines, how to make UX changes, how to contribute large projects (which should tie into design documents), and best practices
Fix part of #1723: Known issues that have come up in discussions
Essential Checklist